Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Dart language to a different bucket of E2E tests on Travis #177

Closed
izeigerman opened this issue Mar 9, 2020 · 7 comments
Closed

Move Dart language to a different bucket of E2E tests on Travis #177

izeigerman opened this issue Mar 9, 2020 · 7 comments

Comments

@izeigerman
Copy link
Member

izeigerman commented Mar 9, 2020

Although the Dart has been configured in .travis.yaml I don't see it's being executed. Eg. recent master build - https://travis-ci.org/BayesWitnesses/m2cgen/jobs/660185796.
Error in the output:

Unknown pytest.mark.dart - is this a typo?  You can register custom marks to avoid this warning

CC: @StrikerRUS

@izeigerman izeigerman changed the title Dart E2E tests are not being executed on Travis E2E tests for Dart language are not being executed on Travis Mar 9, 2020
@izeigerman
Copy link
Member Author

izeigerman commented Mar 9, 2020

Additionally it seems like it's not a great idea to put Dart into the same bucket as R, since R tests already take 24 minutes, while other buckets take only ~4 and 8.5 minutes to complete.

@izeigerman
Copy link
Member Author

Oops, sorry, I've just noticed that it's there for PR builds. We should still move it to a different bucket though.

@izeigerman izeigerman changed the title E2E tests for Dart language are not being executed on Travis Move Dart language to a different bucket of E2E tests on Travis Mar 9, 2020
@StrikerRUS
Copy link
Member

StrikerRUS commented Mar 9, 2020

I'm looking into master jobs: https://travis-ci.org/BayesWitnesses/m2cgen/builds/660185788.
In all buckets only the first language tests are run (c_lang, c_sharp, r_lang).

UPD: pytest issue?..

UPD2: rerunning all Python 3.7 tests in master...

UPD3: during re-running Python 3.7 tests everything seems to be OK - all language tests are executed now.

UPD4: Hope it was a random pytest error. I'm going to update branch in #176 right now. Let's take a look at those builds.

@StrikerRUS
Copy link
Member

Sorry, wrong button. Seems that PR builds are OK. Re-running the rest of master incomplete builds.

@izeigerman
Copy link
Member Author

Hm, yeah. Super weird. Thanks for looking into this!

@StrikerRUS
Copy link
Member

Yes, indeed...

@izeigerman
Copy link
Member Author

izeigerman commented Mar 16, 2020

Seems not to be an issue. Closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants