Attempt to always run tests. #61

Open

brent.edwards wants to merge 9 commits from automatically-run-tests into create-validator

pull from: automatically-run-tests

merge into: cleverdatasets:create-validator

cleverdatasets:master

cleverdatasets:streaming-upload-docker

cleverdatasets:unit-tests-google-tracker-sheet

cleverdatasets:xml-streaming-optimization

cleverdatasets:create-validator

cleverdatasets:auto-excel-update

cleverdatasets:stream-download-convert-upload-merge-15-refactor-rdf-converters

cleverdatasets:streaming-xml

Conversation 0 Commits 9 Files changed 25 +844 -619

brent.edwards commented 2026-02-04 23:28:43 +00:00

Member

Copy link

No description provided.

brent.edwards added 1 commit 2026-02-04 23:28:43 +00:00

First attempt to always run tests. f177b6b06a

brent.edwards added 1 commit 2026-02-05 00:01:57 +00:00

Adding nodejs to every build. 3b64a7c476

brent.edwards added 1 commit 2026-02-05 00:04:10 +00:00

This time, putting the extra steps on the correct file. d7988427b3

brent.edwards added 1 commit 2026-02-05 00:27:40 +00:00

And installing the right software. c3da9ea89c

brent.edwards added 1 commit 2026-02-05 01:11:27 +00:00

Formatting fixes. db74a1ccc4

brent.edwards added 4 commits 2026-02-06 01:23:30 +00:00

style: reorder imports and remove unused variables 8341592990

style: reformat long lines to fit within 88 characters ... c1e8615e8d

Co-authored-by: aider (openrouter/google/gemini-2.5-pro) <aider@aider.chat>

fix: handle None cases for rdf_file and field in dataset_validator.py ... 506e85249a

Co-authored-by: aider (openrouter/openai/o3-mini-high) <aider@aider.chat>

Changes to improve pyright results. b39495e914

Some checks failed

Hide all checks

CI-always / lint (push) Failing after 54s

Details

CI-always / typecheck (push) Failing after 1m0s

Details

CI-always / lint (pull_request) Failing after 53s

Details

CI-always / behave (3.13) (push) Failing after 1m6s

Details

CI-always / typecheck (pull_request) Failing after 58s

Details

CI-always / behave (3.13) (pull_request) Failing after 1m0s

Details

This pull request has changes conflicting with the target branch.

• scripts/convert_rdf_to_hf_dataset_unified.py
• scripts/rdf_to_hf_incremental.py

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin automatically-run-tests:automatically-run-tests

git switch automatically-run-tests

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch create-validator

git merge --no-ff automatically-run-tests

git switch automatically-run-tests

git rebase create-validator

git switch create-validator

git merge --ff-only automatically-run-tests

git switch automatically-run-tests

git rebase create-validator

git switch create-validator

git merge --no-ff automatically-run-tests

git switch create-validator

git merge --squash automatically-run-tests

git switch create-validator

git merge --ff-only automatically-run-tests

git switch create-validator

git merge automatically-run-tests

git push origin create-validator

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

cleverdatasets/dataset-uploader!61

No description provided.