Re: AOO41X Test Builds

2025-07-24 Thread Czesław Wolański
Hi Matthias, On 2025/07/24 12:50:53 Matthias Seidel wrote: > Hi Czesław, > > Happy to "see" you! Thank you. Happy to be "seen" again. > > 2. Issue 110054 – Empty OOo saved as UOF file comes up read only > > I followed the instructions in the report and the dialog box "Document in > > Use" is di

Re: AOO41X Test Builds

2025-07-24 Thread Matthias Seidel
idel a écrit : Hi Dick, Pedro, Thanks for the response! At least we should not have "new" issues. Did you test against the closed ones? https://bz.apache.org/ooo/buglist.cgi?list_id=252135&query_format=advanced&resolution=FIXED&resolution=FIXED_WITHOUT_CODE&target_milest

Re: AOO41X Test Builds

2025-07-24 Thread Czesław Wolański
pelled "Blowfish"? Regards, Czesław Le dim. 20 juil. 2025 à 12:48, Matthias Seidel a écrit : > Hi Dick, Pedro, > > Thanks for the response! At least we should not have "new" issues. > > Did you test against the closed ones? > > > https://b

Re: AOO41X Test Builds

2025-07-20 Thread Matthias Seidel
Hi Dick, Pedro, Thanks for the response! At least we should not have "new" issues. Did you test against the closed ones? https://bz.apache.org/ooo/buglist.cgi?list_id=252135&query_format=advanced&resolution=FIXED&resolution=FIXED_WITHOUT_CODE&target_milestone=4.1.16

Re: AOO41X Test Builds

2025-07-20 Thread Dick Groskamp
Works for me on Win 11 x64 :-) On 2025/07/18 13:26:00 Matthias Seidel wrote: > And of course, feedback is always welcome! > > Regards, Matthias > > Am 16.07.25 um 17:26 schrieb Matthias Seidel: > > Hi All, > > > > New Windows AOO41X Test Builds are ava

Re: AOO41X Test Builds

2025-07-19 Thread Pedro Lino
Working without any issues under Windows 10 x64! Thanks! Best, Pedro > On 07/18/2025 2:26 PM WEST Matthias Seidel wrote: > > > And of course, feedback is always welcome! > > Regards, Matthias > > Am 16.07.25 um 17:26 schrieb Matthias Seidel: > > Hi All, &

Re: AOO41X Test Builds

2025-07-18 Thread Matthias Seidel
And of course, feedback is always welcome! Regards, Matthias Am 16.07.25 um 17:26 schrieb Matthias Seidel: Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google.com/drive/folders/17c2sB4yY2lZI1bNep_ewO4HaYG-dOez5 Regards,    Matthias

AOO41X Test Builds

2025-07-16 Thread Matthias Seidel
Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google.com/drive/folders/17c2sB4yY2lZI1bNep_ewO4HaYG-dOez5 Regards,    Matthias - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org

Re: Unit test improvements and other changes

2025-05-25 Thread Damjan Jovanovic
nd have now pushed these > changes > > to trunk. > > > > > > > > In terms of future developments, maybe we should move the "complex" tests > > (and eventually "unoapi" tests too) from main//qa/complex to > test/? > > That way, we

Re: Unit test improvements and other changes

2025-05-25 Thread Carl Marcum
ot;complex" tests (and eventually "unoapi" tests too) from main//qa/complex to test/? That way, we would have only 2 types of tests: the module-specific unit tests that run during the build, usually using Google Test, and the "subsequent tests" which need a full OpenOffice to

Re: Test refactoring (main/qadevOOo -> test/), i18n issues, Unicode version upgrade

2025-05-13 Thread Keith N. McKenna
Greetings Damjan; Thank you for all your good work, and for jumping in too help the backlog. Regards Keith Arrigo Marchiori wrote: Hello Damjan, On Sun, May 11, 2025 at 10:03:06AM +0200, Damjan Jovanovic wrote: Hi To test my recent work on changing OpenOffice to call ICU only through its

Re: Test refactoring (main/qadevOOo -> test/), i18n issues, Unicode version upgrade

2025-05-12 Thread Arrigo Marchiori
Hello Damjan, On Sun, May 11, 2025 at 10:03:06AM +0200, Damjan Jovanovic wrote: > Hi > > To test my recent work on changing OpenOffice to call ICU only through its > C API, I tried to get the i18n unit tests in main/qade

Test refactoring (main/qadevOOo -> test/), i18n issues, Unicode version upgrade

2025-05-11 Thread Damjan Jovanovic
Hi To test my recent work on changing OpenOffice to call ICU only through its C API, I tried to get the i18n unit tests in main/qadevOOo working. Porting main/qadevOOo tests to test

Re: AOO41X Test Builds

2025-03-17 Thread Dave Fisher
tudio M1 (macOS 15.3.1) machine. >>>> >>>> But it seems Apple has tightened the Gatekeeper? Right mouse click and >>>> "Open" did not work for me, I had to go to the security settings... >>>> >>>> Regards, >>>> >&g

Re: AOO41X Test Builds

2025-03-17 Thread Jim Jagielski
e: >>> >>> Hi Jim, >>> >>> Installed and works on our macStudio M1 (macOS 15.3.1) machine. >>> >>> But it seems Apple has tightened the Gatekeeper? Right mouse click and >>> "Open" did not work for me, I had to go to the

Re: AOO41X Test Builds

2025-03-11 Thread Jim Jagielski
> On Mar 11, 2025, at 8:01 AM, Matthias Seidel > wrote: > > Since the ASF stopped providing space for it, I now use Google Drive. > After all, these are my personal builds, nothing official. Yeah, I was thinking of doing the same... > > For everything more "official" (dev builds, etc.) we c

Re: AOO41X Test Builds

2025-03-11 Thread Matthias Seidel
eeper? Right mouse click and "Open" did not work for me, I had to go to the security settings... Regards, Matthias Am 11.03.25 um 14:04 schrieb Jim Jagielski: And macOS test builds are available here: https://drive.google.com/drive/folders/143ZmyCCK7EVkx-BG8FgZTgBCL8QN6Te4?u

Re: AOO41X Test Builds

2025-03-11 Thread Dave Fisher
rk for me, I had to go to the security settings... >> >> Regards, >> >> Matthias >> >> Am 11.03.25 um 14:04 schrieb Jim Jagielski: >>> And macOS test builds are available here: >>> >>> >>> https://drive.google.com/drive

Re: AOO41X Test Builds

2025-03-11 Thread Jim Jagielski
has tightened the Gatekeeper? Right mouse click and "Open" > did not work for me, I had to go to the security settings... > > Regards, > >Matthias > > Am 11.03.25 um 14:04 schrieb Jim Jagielski: >> And macOS test builds are available here: &

Re: AOO41X Test Builds

2025-03-11 Thread Matthias Seidel
And macOS test builds are available here: https://drive.google.com/drive/folders/143ZmyCCK7EVkx-BG8FgZTgBCL8QN6Te4?usp=sharing On Mar 9, 2025, at 8:03 PM, Matthias Seidel wrote: Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google.com/dri

Re: AOO41X Test Builds

2025-03-11 Thread Jim Jagielski
And macOS test builds are available here: https://drive.google.com/drive/folders/143ZmyCCK7EVkx-BG8FgZTgBCL8QN6Te4?usp=sharing > On Mar 9, 2025, at 8:03 PM, Matthias Seidel > wrote: > > Hi All, > > New Windows AOO41X Test Builds are available for testing: > >

Re: AOO41X Test Builds

2025-03-11 Thread Matthias Seidel
Since the ASF stopped providing space for it, I now use Google Drive. After all, these are my personal builds, nothing official. For everything more "official" (dev builds, etc.) we can use dist.apache.org (dev area). Am 11.03.25 um 12:53 schrieb Jim Jagielski: For these test bui

Re: AOO41X Test Builds

2025-03-11 Thread Jim Jagielski
For these test builds, do we have any ASF space we can use, or should use, to host them? -- Jim "If it is not right, do not do it; if it is not true, do not say it."

Re: AOO41X Test Builds

2025-03-11 Thread Matthias Seidel
/display/OOOUSERS/AOO+4.1.16 Matthias Best, Pedro On 03/10/2025 12:03 AM WET Matthias Seidel wrote: Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google.com/drive/folders/17c2sB4yY2lZI1bNep_ewO4HaYG-dOez5 Regards,    Matthias

Re: macOS test builds of AOO41X starting

2025-03-11 Thread Matthias Seidel
Great! Am 11.03.25 um 12:16 schrieb Jim Jagielski: Subj line sez it all -- Jim "If it is not right, do not do it; if it is not true, do not say it." smime.p7s Description: Kryptografische S/MIME-Signatur

macOS test builds of AOO41X starting

2025-03-11 Thread Jim Jagielski
Subj line sez it all -- Jim "If it is not right, do not do it; if it is not true, do not say it."

Re: AOO41X Test Builds

2025-03-10 Thread Pedro Lino
Hi Matthias Works well under Windows 10 x64 Any particular issues to check? Best, Pedro > On 03/10/2025 12:03 AM WET Matthias Seidel wrote: > > > Hi All, > > New Windows AOO41X Test Builds are available for testing: > > https://drive.google.com/drive/folders/17c

Re: AOO41X Test Builds

2025-03-10 Thread Aivaras Stepukonis
hias Le 10/03/2025 01:03, Matthias Seidel a écrit : Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google.com/drive/folders/17c2sB4yY2lZI1bNep_ewO4HaYG-dOez5 Regards,    Matthias - To unsubs

Re: AOO41X Test Builds

2025-03-10 Thread Matthias Seidel
stallation, but I don't have the instructions at hand. They are somewhere in our Wiki. Regards,    Matthias Le 10/03/2025 01:03, Matthias Seidel a écrit : Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google.com/drive/folders/17c2sB4yY2lZI1bNep

Re: AOO41X Test Builds

2025-03-10 Thread club . acsi
Thanks for that Is it possible to install this build when you already have 4.1.15 on the computer? Does it replace or is it a "dual" installation? Le 10/03/2025 01:03, Matthias Seidel a écrit : Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google

AOO41X Test Builds

2025-03-09 Thread Matthias Seidel
Hi All, New Windows AOO41X Test Builds are available for testing: https://drive.google.com/drive/folders/17c2sB4yY2lZI1bNep_ewO4HaYG-dOez5 Regards,    Matthias smime.p7s Description: Kryptografische S/MIME-Signatur

Re: developer test releases?

2025-02-26 Thread Matthias Seidel
any AOO41X builds that I could test? Regards, Matthias Am 09.12.24 um 13:02 schrieb Jim Jagielski: I'm upgrading my home system which means that the environment that we use for our community builds for macOS and Linux will be changing. Since it's been awhile since we'v

Re: developer test releases?

2025-02-26 Thread Jim Jagielski
st updated our M1 machine (MacStadium) to macOS 15.3. >>> >>> Do you have any AOO41X builds that I could test? >>> >>> Regards, >>> >>>Matthias >>> >>> Am 09.12.24 um 13:02 schrieb Jim Jagielski: >>>> I'm

Re: developer test releases?

2025-02-26 Thread Jim Jagielski
st updated our M1 machine (MacStadium) to macOS 15.3. >>> >>> Do you have any AOO41X builds that I could test? >>> >>> Regards, >>> >>>Matthias >>> >>> Am 09.12.24 um 13:02 schrieb Jim Jagielski: >>>> I'm

Test

2025-02-26 Thread club . acsi
Did you received?

Re: [PR] pre-commit(end-of-file-fixer): auto fix the `test` directory [openoffice]

2025-02-11 Thread via GitHub
Pilot-Pirx merged PR #275: URL: https://github.com/apache/openoffice/pull/275 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice

[PR] pre-commit(end-of-file-fixer): auto fix the `test` directory [openoffice]

2025-02-10 Thread via GitHub
jbampton opened a new pull request, #275: URL: https://github.com/apache/openoffice/pull/275 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-

Re: developer test releases?

2025-02-03 Thread Matthias Seidel
Hi Jim, Am 03.02.25 um 09:42 schrieb Jim Jagielski: On Jan 30, 2025, at 9:44 AM, Matthias Seidel wrote: Hi Jim, I just updated our M1 machine (MacStadium) to macOS 15.3. Do you have any AOO41X builds that I could test? Regards, Matthias Am 09.12.24 um 13:02 schrieb Jim Jagielski

Re: developer test releases?

2025-02-03 Thread Jim Jagielski
> On Jan 30, 2025, at 9:44 AM, Matthias Seidel > wrote: > > Hi Jim, > > I just updated our M1 machine (MacStadium) to macOS 15.3. > > Do you have any AOO41X builds that I could test? > > Regards, > >Matthias > > Am 09.12.24 um 13:02 schri

Re: developer test releases?

2025-01-30 Thread Matthias Seidel
Hi Jim, I just updated our M1 machine (MacStadium) to macOS 15.3. Do you have any AOO41X builds that I could test? Regards,    Matthias Am 09.12.24 um 13:02 schrieb Jim Jagielski: I'm upgrading my home system which means that the environment that we use for our community builds for

Re: developer test releases?

2024-12-14 Thread Matthias Seidel
mailto:keith.mcke...@comcast.net.invalid>> wrote: Marcus wrote: Am 09.12.24 um 13:02 schrieb Jim Jagielski: I'm upgrading my home system which means that the environment that we use for our community builds for macOS and Linux will be changing. Since it's been awhile since we&

Re: developer test releases?

2024-12-14 Thread Arrigo Marchiori
em which means that the environment that we > >>>>> use for our community builds for macOS and Linux will be changing. > >>>>> Since it's been awhile since we've done any test releases, should we > >>>>> check that we all can still

Re: developer test releases?

2024-12-10 Thread Dave Fisher
te: >>> >>> Marcus wrote: >>>> Am 09.12.24 um 13:02 schrieb Jim Jagielski: >>>>> I'm upgrading my home system which means that the environment that we >>>>> use for our community builds for macOS and Linux will be changing. >>>

Re: developer test releases?

2024-12-10 Thread Jim Jagielski
t;>> I'm upgrading my home system which means that the environment that we >>>> use for our community builds for macOS and Linux will be changing. >>>> Since it's been awhile since we've done any test releases, should we >>>> check that we all can

Re: developer test releases?

2024-12-10 Thread Gavin McDonald
anging. > >> Since it's been awhile since we've done any test releases, should we > >> check that we all can still do them as well as maybe see what still is > >> holding us up for any official releases? > > > > for me it makes sense to test if buildi

Re: developer test releases?

2024-12-09 Thread Keith McKenna
Marcus wrote: Am 09.12.24 um 13:02 schrieb Jim Jagielski: I'm upgrading my home system which means that the environment that we use for our community builds for macOS and Linux will be changing. Since it's been awhile since we've done any test releases, should we check that w

Re: developer test releases?

2024-12-09 Thread Marcus
Am 09.12.24 um 13:02 schrieb Jim Jagielski: I'm upgrading my home system which means that the environment that we use for our community builds for macOS and Linux will be changing. Since it's been awhile since we've done any test releases, should we check that we all can still

developer test releases?

2024-12-09 Thread Jim Jagielski
I'm upgrading my home system which means that the environment that we use for our community builds for macOS and Linux will be changing. Since it's been awhile since we've done any test releases, should we check that we all can still do them as well as maybe see what still is ho

Re: Unit test improvements and other changes

2024-07-18 Thread Matthias Seidel
d the following: - The "complex" tests (usually in /qa/complex) now all only use JUnit to run. JUnit is far more widely known, and uses annotations such as "@Test" and "@Before" / "@After", instead of the older and more error-prone methods used by qadevOO'

Unit test improvements and other changes

2024-07-17 Thread Damjan Jovanovic
nit is far more widely known, and uses annotations such as "@Test" and "@Before" / "@After", instead of the older and more error-prone methods used by qadevOO's ComplexTestCase class, such as overriding method names and returning a list of strings naming the methods t

Re: [PR] misc: fix spelling, fix test [openoffice]

2023-12-01 Thread via GitHub
Pilot-Pirx commented on code in PR #189: URL: https://github.com/apache/openoffice/pull/189#discussion_r1412429050 ## main/qadevOOo/tests/basic/ifc/awt/XListBox/awt_XListBox.xba: ## Review Comment: Good find! -- This is an automated message from the Apache Git Service.

Re: [PR] misc: fix spelling, fix test [openoffice]

2023-12-01 Thread via GitHub
Pilot-Pirx merged PR #189: URL: https://github.com/apache/openoffice/pull/189 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice

[PR] misc: fix spelling, fix test [openoffice]

2023-12-01 Thread via GitHub
jbampton opened a new pull request, #189: URL: https://github.com/apache/openoffice/pull/189 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-

[GitHub] [openoffice] cbmarcum merged pull request #170: updated trunk test readme for being the standalone test branch

2023-02-12 Thread via GitHub
cbmarcum merged PR #170: URL: https://github.com/apache/openoffice/pull/170 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.a

[GitHub] [openoffice] cbmarcum opened a new pull request, #170: updated trunk test readme for being the standalone test branch

2023-02-12 Thread via GitHub
cbmarcum opened a new pull request, #170: URL: https://github.com/apache/openoffice/pull/170 and current tests for other branches. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific com

Re: AOO4114 Windows Test builds

2022-12-06 Thread Matthias Seidel
Hi Carl, Am 06.12.22 um 20:44 schrieb Carl Marcum: > Hi Matthias, > > On 12/2/22 03:53, Matthias Seidel wrote: >> Hi all, >> >> I just finished a new Test build for Windows. This is my first AOO41X >> build with Cygwin64. >> >> I don't expect

Re: AOO4114 Windows Test builds

2022-12-06 Thread Carl Marcum
Hi Matthias, On 12/2/22 03:53, Matthias Seidel wrote: Hi all, I just finished a new Test build for Windows. This is my first AOO41X build with Cygwin64. I don't expect problems, but if you have the time, please test it: https://home.apache.org/~mseidel/AOO-builds/AOO-4114-Test/ Re

AOO4114 Windows Test builds

2022-12-02 Thread Matthias Seidel
Hi all, I just finished a new Test build for Windows. This is my first AOO41X build with Cygwin64. I don't expect problems, but if you have the time, please test it: https://home.apache.org/~mseidel/AOO-builds/AOO-4114-Test/ Regards,    Matthias smime.p7s Description: S/MIME Cryptogr

[GitHub] [openoffice] cbmarcum merged pull request #156: Tab function test document and test

2022-09-24 Thread GitBox
cbmarcum merged PR #156: URL: https://github.com/apache/openoffice/pull/156 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.a

[GitHub] [openoffice] cbmarcum opened a new pull request, #156: Tab function test document and test

2022-09-24 Thread GitBox
cbmarcum opened a new pull request, #156: URL: https://github.com/apache/openoffice/pull/156 A test document and added it to TestFormulaDocs.java Refs i19221 https://bz.apache.org/ooo/show_bug.cgi?id=19221 Patch-By: Czesław Wolański -- This is an automated message from

[GitHub] [openoffice] cbmarcum merged pull request #152: Refs i126272 - add test and test document for testing Basic comment in single-line if statements

2022-06-10 Thread GitBox
cbmarcum merged PR #152: URL: https://github.com/apache/openoffice/pull/152 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.a

[GitHub] [openoffice] cbmarcum opened a new pull request, #152: Refs i126272 - add test and test document for testing Basic comment in single-line if statements

2022-06-10 Thread GitBox
cbmarcum opened a new pull request, #152: URL: https://github.com/apache/openoffice/pull/152 This can be cherry-picked for AOO42X but a version of it is already covered in AOO41X. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

[GitHub] [openoffice] cbmarcum opened a new pull request, #149: Fix test formula docs

2022-05-29 Thread GitBox
cbmarcum opened a new pull request, #149: URL: https://github.com/apache/openoffice/pull/149 updated TestFormulaDocs test to be a parameterized test to better see which document failed. Fixed late screenshots on failures. Added timeout for dialog hangs when running tests against

[GitHub] [openoffice] cbmarcum merged pull request #148: Fix sample test AOOTest for late failure screenshots and fix an assertion text incorrectly changed in a code cleanup.

2022-05-14 Thread GitBox
cbmarcum merged PR #148: URL: https://github.com/apache/openoffice/pull/148 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.a

[GitHub] [openoffice] cbmarcum opened a new pull request, #148: Fix sample test AOOTest for late failure screenshots and fix an assertion text incorrectly changed in a code cleanup.

2022-05-14 Thread GitBox
cbmarcum opened a new pull request, #148: URL: https://github.com/apache/openoffice/pull/148 Updated AOOTest to use newer API and fix late screenshots on failures. Fixed BasicFunctionTest.testFind assertion because of a previous code cleanup that changed the assertion text causing the test

[GitHub] [openoffice] cbmarcum merged pull request #145: Make the automated test suite standalone from the office build

2022-04-15 Thread GitBox
cbmarcum merged PR #145: URL: https://github.com/apache/openoffice/pull/145 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openoffice.a

Re: 4.1.12-dev developer test builds...

2022-04-14 Thread Marcus
some more days... That way people get the opportunity to test the builds and we also could integrate the latest English dictionary on Tuesday(?). My latest build for Windows can be found here: https://home.apache.org/~mseidel/Apache_OpenOffice_4.1.12_Win_x86_install_en-US_Test.exe Looking forwa

Re: 4.1.12-dev developer test builds...

2022-04-12 Thread Matthias Seidel
;>>>> >>>>>> http://home.apache.org/~jim/AOO-builds/ >>>>> Thanks! >>>>> >>>>> I tested your builds on Ubuntu 16.04 (64bit) and macOS 12. Working as >>>>> expected. >>>>> >&

Re: 4.1.12-dev developer test builds...

2022-04-11 Thread Matthias Seidel
Jagielski: >>>>> ... Are available at >>>>> >>>>> http://home.apache.org/~jim/AOO-builds/ >>>> Thanks! >>>> >>>> I tested your builds on Ubuntu 16.04 (64bit) and macOS 12. Working as >>>> expected. >&g

Re: 4.1.12-dev developer test builds...

2022-04-11 Thread Jim Jagielski
g as >>> expected. >>> >>>> Assuming these look good, we can progress to an RC1 >>> Given that there was not so much response until now I would propose to >>> wait some more days... >>> >>> That way people get the opportunity to t

Re: 4.1.12-dev developer test builds...

2022-04-10 Thread Matthias Seidel
/~mseidel/AOO-builds/AOO-4112-Test/ Regards,    Matthias > Regards > C. Verbrèghe (Manjiro) > > Le ven. 25 mars 2022 à 13:25, Jim Jagielski a écrit : > >> ... Are available at >> >>http://home.apache.org/~jim/AOO-builds/ >> >&g

Re: 4.1.12-dev developer test builds...

2022-04-10 Thread Corentin Verbrèghe
Hi, Is there a Windows version of the build? Unfortunately, I have neither a Mac nor a PC running on the GNU-Linux kernel. Regards C. Verbrèghe (Manjiro) Le ven. 25 mars 2022 à 13:25, Jim Jagielski a écrit : > ... Are available at > >http://home.apache.org/~jim/AOO-builds/ > > Assuming these

[GitHub] [openoffice] cbmarcum opened a new pull request, #145: Make the automated test suite standalone from the office build

2022-04-09 Thread GitBox
cbmarcum opened a new pull request, #145: URL: https://github.com/apache/openoffice/pull/145 This change has been discussed on the qa@ list [1] and more recently on the dev@ list [2] and my Fosdem 2022 talk from February 2022. See the README.md for more information. [1] https://lists

Re: 4.1.12-dev developer test builds...

2022-04-09 Thread Matthias Seidel
> >>>> I tested your builds on Ubuntu 16.04 (64bit) and macOS 12. Working as >>>> expected. >>>> >>>>> Assuming these look good, we can progress to an RC1 >>>> Given that there was not so much response until now I would propose to

Re: [DISCUSS] [QA AUTOMATION] merging standalone-test branch into trunk

2022-04-09 Thread Carl Marcum
Hi Damjan, On 4/3/22 9:34 AM, Damjan Jovanovic wrote: On Sun, Mar 27, 2022 at 9:44 PM Carl Marcum wrote: Hi All, Hi I want to get some opinions on whether to merge my work on standalone test automation into trunk and possibly AOO42X and AOO41X or leave it in a branch and use it from

Re: 4.1.12-dev developer test builds...

2022-04-07 Thread Marcus
was not so much response until now I would propose to wait some more days... That way people get the opportunity to test the builds and we also could integrate the latest English dictionary on Tuesday(?). My latest build for Windows can be found here: https://home.apache.org/~mseidel

Re: 4.1.12-dev developer test builds...

2022-04-07 Thread Matthias Seidel
Hi Aivaras, Am 07.04.22 um 17:56 schrieb Aivaras Stepukonis: > A new release is welcome! > > Keep up your good work! Thank you for the kind words! Do you have a chance to test this build (not the latest revision): https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/Full%20Ins

Re: 4.1.12-dev developer test builds...

2022-04-07 Thread Aivaras Stepukonis
A new release is welcome! Keep up your good work! -- Pagarbiai / Sincerely, 📧 Aivaras Stepukonis 2022-04-07 12:21, Matthias Seidel rašė: So, basically only three person are interested in a new release...:-(

Re: 4.1.12-dev developer test builds...

2022-04-07 Thread Carl Marcum
that there was not so much response until now I would propose to wait some more days... That way people get the opportunity to test the builds and we also could integrate the latest English dictionary on Tuesday(?). My latest build for Windows can be found here: https://home.apache.org/~mseidel

Re: 4.1.12-dev developer test builds...

2022-04-07 Thread Matthias Seidel
Assuming these look good, we can progress to an RC1 >>> Given that there was not so much response until now I would propose to >>> wait some more days... >>> >>> That way people get the opportunity to test the builds and we also could >>> integrate the la

Re: 4.1.12-dev developer test builds...

2022-04-07 Thread Matthias Seidel
s >> expected. >> >>> Assuming these look good, we can progress to an RC1 >> Given that there was not so much response until now I would propose to >> wait some more days... >> >> That way people get the opportunity to test the builds and we a

Re: 4.1.12-dev developer test builds...

2022-04-05 Thread Pedro Lino
> On 04/05/2022 2:24 PM Matthias Seidel wrote: > > > Hi Jim, > > Am 05.04.22 um 14:44 schrieb Jim Jagielski: > > Are we ready for a RC1? > > *I* think we are... ;-) +1 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.ap

Re: 4.1.12-dev developer test builds...

2022-04-05 Thread Matthias Seidel
here was not so much response until now I would propose to >> wait some more days... >> >> That way people get the opportunity to test the builds and we also could >> integrate the latest English dictionary on Tuesday(?). >> >> My latest build for Windows ca

Re: 4.1.12-dev developer test builds...

2022-04-05 Thread Jim Jagielski
your builds on Ubuntu 16.04 (64bit) and macOS 12. Working as > expected. > >> Assuming these look good, we can progress to an RC1 > Given that there was not so much response until now I would propose to > wait some more days... > > That way people get the opportunity to test t

Re: [DISCUSS] [QA AUTOMATION] merging standalone-test branch into trunk

2022-04-03 Thread Damjan Jovanovic
On Sun, Mar 27, 2022 at 9:44 PM Carl Marcum wrote: > Hi All, > Hi I want to get some opinions on whether to merge my work on standalone > test automation into trunk and possibly AOO42X and AOO41X or leave it in > a branch and use it from there. > Six months ago I posted this

[GitHub] [openoffice] cbmarcum merged pull request #144: Refs #i128450# - disabled smb host only test

2022-03-27 Thread GitBox
cbmarcum merged pull request #144: URL: https://github.com/apache/openoffice/pull/144 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr

[GitHub] [openoffice] cbmarcum opened a new pull request #144: Refs #i128450# - disabled smb host only test

2022-03-27 Thread GitBox
cbmarcum opened a new pull request #144: URL: https://github.com/apache/openoffice/pull/144 per this email thread: https://lists.apache.org/thread/k1m3wqz04bj8b5kdg814h24qf45sv811 AOO keeps appending a final / thus changing the intent of the test. -- This is an automated message from

[DISCUSS] [QA AUTOMATION] merging standalone-test branch into trunk

2022-03-27 Thread Carl Marcum
Hi All, I want to get some opinions on whether to merge my work on standalone test automation into trunk and possibly AOO42X and AOO41X or leave it in a branch and use it from there. Six months ago I posted this [1] on qa@ and cc'd this list about the work and haven't got an

[GitHub] [openoffice] cbmarcum merged pull request #143: Refs #i128505# - testTableBorderLineStyle flaky test

2022-03-27 Thread GitBox
cbmarcum merged pull request #143: URL: https://github.com/apache/openoffice/pull/143 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr

[GitHub] [openoffice] cbmarcum opened a new pull request #143: Refs #i128505# - testTableBorderLineStyle flaky test

2022-03-27 Thread GitBox
cbmarcum opened a new pull request #143: URL: https://github.com/apache/openoffice/pull/143 testTableBorderLineStyle() was entering 0.55" instead of 0.50" at line 199 because the ctrl-a wasn't selecting all of the cell contents and leaving a 5 in the cell. then when typing in 0.5 it became

Re: 4.1.12-dev developer test builds...

2022-03-27 Thread Matthias Seidel
e was not so much response until now I would propose to wait some more days... That way people get the opportunity to test the builds and we also could integrate the latest English dictionary on Tuesday(?). My latest build for Windows can be found here: https://home.apache.

Re: 4.1.12-dev developer test builds...

2022-03-26 Thread Pedro Lino
Hi Jim Works perfectly under Ubuntu 20.04.4 x64 (and includes the dedicatory to Joerg) +1 to move on to RC1 I will be away until the 5th of April but am available to build, test and vote after that Regards, Pedro > On 03/25/2022 12:24 PM Jim Jagielski wrote: > > > ... Are

4.1.12-dev developer test builds...

2022-03-25 Thread Jim Jagielski
... Are available at http://home.apache.org/~jim/AOO-builds/ Assuming these look good, we can progress to an RC1 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openof

AOO41X Windows Test Builds

2022-03-01 Thread Matthias Seidel
Hi all, You can find my latest Test Builds for Windows here: https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ Regards,    Matthias smime.p7s Description: S/MIME Cryptographic Signature

Re: [QA AUTOMATION] Standalone Tests now available in standalone-test branch

2021-09-30 Thread Marcus
Am 30.09.21 um 04:02 schrieb Carl Marcum: Just an FYI on the status of my work on allowing the automated test suites to compile and run tests without a working AOO build environment. I've started a new branch standalone-test [1] with a README file explaining the usage. [...] thanks for

[QA AUTOMATION] Standalone Tests now available in standalone-test branch

2021-09-29 Thread Carl Marcum
Hi All, cc: dev@ Just an FYI on the status of my work on allowing the automated test suites to compile and run tests without a working AOO build environment. I've started a new branch standalone-test [1] with a README file explaining the usage. So far I've been able to run tests o

[GitHub] [openoffice] cbmarcum merged pull request #136: Make automated test suites standalone

2021-09-22 Thread GitBox
cbmarcum merged pull request #136: URL: https://github.com/apache/openoffice/pull/136 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr

[GitHub] [openoffice] cbmarcum opened a new pull request #136: Make automated test suites standalone

2021-09-22 Thread GitBox
idlc, and changes it to depend on the ones in the office under test which is passed as the openoffice.home env variable to ant compile and the run scripts. This allows anyone to run the QA test suites against any office directory as long is it has an SDK installed in it without needing the

Re: Test builds AOO 4.1.11

2021-08-23 Thread Jim Jagielski
And the macOS, Linux64 and Linux32 bit builds can be found at: https://home.apache.org/~jim/AOO-builds/AOO-4.1.11-test/ Cheers! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail

Re: Test builds AOO 4.1.11

2021-08-19 Thread Matthias Seidel
Am 19.08.21 um 19:00 schrieb Jim Jagielski: > HEAD on origin/AOO41X? I built 31fa317f66, that is one commit behind HEAD. Shouldn't make a big difference since these are only test builds. Matthias > >> On Aug 19, 2021, at 10:08 AM, Matthias Seidel >> wrote: >> &g

  1   2   3   4   5   6   7   8   >