Hi,
I moved all PHP tests from Travis to Github Actions because tests for
PHP Editor were running too long. Travis always timed out.
It was easier to setup Windows build for PHP Editor in Github Actions.
Some tests were OK under Linux but broken when run on Windows, some
tests were broken from different reasons (files missing from donation,
different dorectory separator).
Rough overview of fixes:
https://github.com/apache/netbeans/pulls?q=is%3Apr+author%3AKacerCZ+is%3Aclosed+milestone%3A12.1+tests
I stareted conversion of other jobs
(https://github.com/apache/netbeans/pull/2708) but stopped given current
status of Github Actions
(https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status)
Regards,
Tom
On 16. 04. 21 16:25, Eric Bresie wrote:
Where is the configuration for these build checks setup? Is there a
specific yaml or part of a build script someplace?
Did more poking here and see
- .github/workflows/main.xml file
- Assume this drives the initial "check" jobs.
- This has the "Test" job with limited sub-tests defined, compared to
the "Test PHP Cluster" which defines a lot more of the php sub
test cases.
- travis.yaml file
- Assume this is used in the last phase in the "Travis CI" portion.
- This has a lot more test coverage defined here for other areas.
So at the moment some testing is done at the github action context and some
done in the "travis" context.
So there are more tests in the github contexts for php and less for other
areas while in the travis CI context there is more test coverage in other
areas and less in php. Assume there is additional time that I was not
seeing in the travis context for others tests compared to more time for php
in the github action context.
Assume this split between the two areas for testing is related to the
discussion on "TravisCI vs Jenkins vs GitHub Actions" [1]. Sounded like
there may be some resource concerns and/or Apache infrastructure
Will the builds continue to use github actions + travis or are there any
plans to migrate in one way or another?
If moving towards github action based, assume other tests would need to be
moved to the github testing (i.e. more "Test x Cluster" with applicable run
tests for each as applicable in main.xml).
Was anything decided on "Jenkins" usage?
References
[1]
https://lists.apache.org/thread.html/rc3a7ad290b004557c69d8cac7f5bd4825ca3d230b626641a8565164b%40%3Cdev.netbeans.apache.org%3E
Eric Bresie
[email protected]
On Fri, Apr 16, 2021 at 8:10 AM Geertjan Wielenga
<[email protected]> wrote:
Because the others have less tests.
Gj
On Fri, Apr 16, 2021 at 2:59 PM Eric Bresie <[email protected]> wrote:
Let me change the question a little...Why are all the others quicker
compared to the php side?
Do the other clusters / jobs / checks not get tested in the same way
(i.e.
only a subset of tests compare to all tests in php test if so why)? Are
there fewer tests (I would assume not as I've run some of the unit tests
on
just one project which ? Do the tests in other context require some "UI"
based tests not possible at build time compared to php which can be UI
less
(i.e. request/response)?Are the other tests faster compared to slower php
tests? Does the php test require starting/stopping some php server for
use
during the test?
Just a snapshot of few occurrences, not the "Test PHP Cluster" check
compared to others
For the Windows build
[image: image.png]
For the Linux of PHP cluster
[image: image.png]
Where is the configuration for these build checks setup? Is there a
specific yaml or part of a build script someplace?
Eric Bresie
[email protected]
On Thu, Apr 15, 2021 at 2:51 PM Junichi Yamamoto <[email protected]>
wrote:
Because PHP editor has many unit tests.
Junichi
On Mon, Apr 12, 2021 at 5:43 AM Eric Bresie <[email protected]> wrote:
I was curious...any reason during the build checks that Test PHP
Cluster takes so long? It seems like most of the checks are about 1 to
10
minutes but this seems to take closer to an hour.
I see a lot of things like the below.
[junit] ------------- Standard Error -----------------
9931 (https://github.com/apache/netbeans/runs/2318602490#step:7:9931)
[junit] Apr 11, 2021 8:36:45 PM
org.netbeans.modules.masterfs.watcher.Watcher getNotifierForPlatform
9932 (https://github.com/apache/netbeans/runs/2318602490#step:7:9932)
[junit] INFO: Native file watcher is disabled
9933 (https://github.com/apache/netbeans/runs/2318602490#step:7:9933)
[junit] Apr 11, 2021 8:36:46 PM
org.netbeans.modules.settings.RecognizeInstanceObjects$MSL <clinit>
9934 (https://github.com/apache/netbeans/runs/2318602490#step:7:9934)
[junit] WARNING: Not listening on module system
9935 (https://github.com/apache/netbeans/runs/2318602490#step:7:9935)
[junit] Apr 11, 2021 8:36:47 PM
org.netbeans.modules.php.editor.parser.GSFPHPParser <clinit>
9936 (https://github.com/apache/netbeans/runs/2318602490#step:7:9936)
[junit] INFO: Parsing of big PHP files enabled: false (max size:
5,000,000)
Eric Bresie
[email protected] (mailto:[email protected])
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
