Move Dart language to a different bucket of E2E tests on Travis
See original GitHub issueAlthough 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
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Building a Dart Project - Travis CI Docs
This guide covers build environment and configuration topics specific to Dart projects. Please make sure to read our Tutorial and general build ...
Read more >Run Flutter e2e tests on Travis CI - panmari's blog
Integration tests play an important role in making sure you don't break your app. In this blog post I go over the important...
Read more >investigate sharding the e2e tests on travis · Issue #972 - GitHub
dart -lang / build Public ... investigate sharding the e2e tests on travis #972 ... split e2e tests into 4 shards #973.
Read more >Flutter Integration Tests with Travis CI - Stack Overflow
I'll be updating the yaml code below myself every time a useful iteration arrives. language: dart env: global: - DARTSDK=./flutter/bin/cache ...
Read more >Testing AWS Lambda Functions and S3 with Node.JS
I needed to write tests for AWS Lambda functions that receive JSON ... I have several tests in different files testing different use...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.
Seems not to be an issue. Closing this for now.